Skip to content

Conversation

younies
Copy link
Member

@younies younies commented Sep 19, 2025

Description

The issue occurred because unit parsing failures were not checked or the status reset. As a result, if one unit failed to parse, the status carried an error and caused all subsequent test cases to fail.

Changes made:

  • Updated expected formats tests for unit aliases in both C++ and Java test files.
  • Refactored test cases to use unique_ptr for MeasureUnit in C++ and adjusted the constructor in Java.
  • Introduced logging for known issues related to unit aliases.

Note: This issue still exists — ICU-23222.

Checklist

  • Required: Issue filed: ICU-23105
  • Required: The PR title must be prefixed with a JIRA Issue number. Example: "ICU-1234 Fix xyz"
  • Required: Each commit message must be prefixed with a JIRA Issue number. Example: "ICU-1234 Fix xyz"
  • Issue accepted (done by Technical Committee after discussion)
  • Tests included, if applicable
  • API docs and/or User Guide docs changed or added, if applicable

…en the units are not parsable

- Refactor test cases to use unique_ptr for MeasureUnit in C++ and adjust constructor in Java.
- Introduce logging for known issues related to unit aliases to ensure compatibility with callers.
- Update expected formats for unit aliases in both C++ and Java test files.
@younies younies force-pushed the ensure-unit-aliases branch from a291bdc to 65a9177 Compare September 19, 2025 10:26
@jira-pull-request-webhook
Copy link

Notice: the branch changed across the force-push!

  • icu4c/source/test/intltest/numbertest_api.cpp is different

View Diff Across Force-Push

~ Your Friendly Jira-GitHub PR Checker Bot

@younies younies marked this pull request as ready for review September 19, 2025 10:30
@younies younies requested a review from pedberg-icu September 19, 2025 10:30
@younies younies merged commit e862a5f into unicode-org:main Sep 19, 2025
103 checks passed
@younies younies deleted the ensure-unit-aliases branch September 19, 2025 21:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants